SherbyNet - /page/wikibook/entry.mu

Micron Document

`:top

In `F33f`_`[computing`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Computing]`_`f, a `!distributed cache`! is an extension of the traditional concept of `F33f`_`[cache`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Cache_(computing)]`_`f used in a single `F33f`_`[locale`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Locale_(computer_hardware)]`_`f. A distributed cache may span multiple servers so that it can grow in size and in transactional capacity. It is mainly used to store application data residing in `F33f`_`[database`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Database]`_`f and web `F33f`_`[session`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Session_(computer_science)]`_`f data. The idea of distributed caching`:cite-ref-1[`F5bf`_`[1`#cite-note-1]`_`f] has become feasible now because `F33f`_`[main memory`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Random-access_memory]`_`f has become very cheap and `F33f`_`[network cards`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Network_interface_controller]`_`f have become very fast, with 1 Gbit now standard everywhere and 10 Gbit gaining traction. Also, a distributed cache works well on lower cost machines usually employed for `F33f`_`[web servers`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Web_server]`_`f as opposed to `F33f`_`[database servers`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Database_server]`_`f which require expensive hardware.`:cite-ref-2[`F5bf`_`[2`#cite-note-2]`_`f] An emerging internet architecture known as `F33f`_`[Information-centric networking`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Information-centric_networking]`_`f (ICN) is one of the best examples of a distributed cache network. The ICN is a network level solution hence the existing distributed network cache management schemes are not well suited for ICN.`:cite-ref-3[`F5bf`_`[3`#cite-note-3]`_`f] In the `F33f`_`[supercomputer`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Supercomputer]`_`f environment, distributed cache is typically implemented in the form of `F33f`_`[burst buffer`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Burst_buffer]`_`f.

In distributed caching, each cache key is assigned to a specific `F33f`_`[shard`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Shard_(database_architecture)]`_`f (a.k.a. partition). There are different sharding strategies:`:cite-ref-4[`F5bf`_`[4`#cite-note-4]`_`f]

• Modulus sharding

• Range-based sharding

• `F33f`_`[Consistent hashing`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Consistent_hashing]`_`f evenly distributes cache keys across shards, even if some of the shards crash or become unavailable.`:cite-ref-5[`F5bf`_`[5`#cite-note-5]`_`f]

>>Contents

• `F0af`_`[Examples`#examples]`_`f

• `F0af`_`[See also`#see-also]`_`f

• `F0af`_`[References`#references]`_`f

-─

>>Examples

• `F33f`_`[Aerospike`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Aerospike_(database)]`_`f

• `F33f`_`[Apache Ignite`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Apache_Ignite]`_`f

• `F33f`_`[Couchbase`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Couchbase_Server]`_`f

• `F33f`_`[Ehcache`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Ehcache]`_`f

• `F33f`_`[GigaSpaces`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=GigaSpaces]`_`f

• `F33f`_`[Hazelcast`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Hazelcast]`_`f

• `F33f`_`[Infinispan`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Infinispan]`_`f

• `F33f`_`[Memcached`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Memcached]`_`f

• `F33f`_`[Oracle Coherence`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Oracle_Coherence]`_`f

• `F33f`_`[Riak`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Riak]`_`f

• `F33f`_`[Redis`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Redis]`_`f

• `F33f`_`[Tarantool`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Tarantool]`_`f

• Velocity/AppFabric

>>See also

• `F33f`_`[Cache algorithms`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Cache_algorithms]`_`f

• `F33f`_`[Cache coherence`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Cache_coherence]`_`f

• `F33f`_`[Cache-oblivious algorithm`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Cache-oblivious_algorithm]`_`f

• `F33f`_`[Cache stampede`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Cache_stampede]`_`f

• `F33f`_`[Cache language model`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Cache_language_model]`_`f

• `F33f`_`[Database cache`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Database_cache]`_`f

• `F33f`_`[Cache manifest in HTML5`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Cache_manifest_in_HTML5]`_`f

>>References

`:cite-note-1`!1.`! `F0af`_`[↑`#cite-ref-1]`_`f `:citerefpaulz-fei2001`aPaul, S; Z Fei (1 February 2001). "Distributed caching with centralized control". `*Computer Communications`*. `!24`! (2): 256–268. `F33f`_`[CiteSeerX`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=CiteSeerX_(identifier)]`_`f 10.1.1.38.1094. `F33f`_`[doi`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Doi_(identifier)]`_`f:10.1016/S0140-3664(00)00322-4.

`:cite-note-2`!2.`! `F0af`_`[↑`#cite-ref-2]`_`f `:citerefkhan`aKhan, Iqbal. "Distributed Caching on the Path To Scalability". `*MSDN`* (July 2009). Retrieved 30 March 2012.

`:cite-note-3`!3.`! `F0af`_`[↑`#cite-ref-3]`_`f `:citerefbilal-muhammad2017`aBilal, Muhammad; et al. (2017). "A Cache Management Scheme for Efficient Content Eviction and Replication in Cache Networks". `*IEEE Access`*. `!5`!: 1692–1701. `F33f`_`[arXiv`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ArXiv_(identifier)]`_`f:1702.04078. `F33f`_`[Bibcode`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Bibcode_(identifier)]`_`f:2017arXiv170204078B. `F33f`_`[doi`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Doi_(identifier)]`_`f:10.1109/ACCESS.2017.2669344. `F33f`_`[S2CID`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=S2CID_(identifier)]`_`f 14517299.

`:cite-note-4`!4.`! `F0af`_`[↑`#cite-ref-4]`_`f `*Foundations of Scalable Systems`*. O'Reilly Media. 2022. `F33f`_`[ISBN`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ISBN_(identifier)]`_`f 9781098106034.

`:cite-note-5`!5.`! `F0af`_`[↑`#cite-ref-5]`_`f `*Designing Distributed Systems Patterns and Paradigms for Scalable, Reliable Services`*. O'Reilly Media. 2018. `F33f`_`[ISBN`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ISBN_(identifier)]`_`f 9781491983607.

`c`F0af`_`[↑ Back to top`#top]`_`f`a